Home system including a portable fob having a rotary menu and a display

ABSTRACT

A home wellness system includes a server having a wireless transceiver, a plurality of sensors each of which has a wireless transceiver adapted to communicate sensor information to the server wireless transceiver, and a portable display and configuration fob. The portable fob includes a rotary thumbwheel encoder, a display and a wireless transceiver communicating with the server wireless transceiver. The thumbwheel encoder and the display cooperate to provide a first rotary menu for displaying the sensor information of the sensors and a second rotary menu for configuring the sensors.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is related to commonly assigned, concurrently filed:

-   -   U.S. patent application Ser. No. ______, filed ______, 2003,        entitled “Home System Including A Portable Fob Having A Display”        (Attorney Docket No. 03-mEDP-244); and    -   U.S. patent application Ser. No. ______, filed ______, 2003,        entitled “Home System Including A Portable Fob Mating With        System Components” (Attorney Docket No. 03-mEDP-244B).

BACKGROUND OF THE INVENTION

1. Field of the Invention

This invention relates generally to home systems and, more particularly,to home systems employing wireless communications, such as, for example,a wireless local area network (WLAN) or a low rate-wireless personalarea network (LR-WPAN).

2. Background Information

Wireless communication networks are an emerging new technology, whichallows users to access information and services electronically,regardless of their geographic position.

All nodes in ad-hoc networks are potentially mobile and can be connecteddynamically in an arbitrary manner. All nodes of these networks behaveas routers and take part in discovery and maintenance of routes to othernodes in the network. For example, ad-hoc networks are very useful inemergency search-and-rescue operations, meetings or conventions in whichpersons wish to quickly share information, and in data acquisitionoperations in inhospitable terrains.

An ad-hoc mobile communication network comprises a plurality of mobilehosts, each of which is able to communicate with its neighboring mobilehosts, which are a single hop away. In such a network, each mobile hostacts as a router forwarding packets of information from one mobile hostto another. These mobile hosts communicate with each other over awireless media, typically without any infra-structured (or wired)network component support.

One type of on-demand ad-hoc routing protocol is Dynamic Source Routing(DSR). A conventional DSR network enables communications between anydevices in such network by discovering communication routes to otherdevices in the network. See, for example, Johnson et al., “DynamicSource Routing in Ad Hoc Wireless Networks”, Mobile Computing, 1996.Dynamic Source Routing for mobile communication networks avoids periodicroute advertisements because route caches are used to store sourceroutes that a mobile host has learned over time. A combination ofpoint-to-point and broadcast routing using the connection-orientedpacket forwarding approach is used. Routes are source-initiated anddiscovered via a route discovery protocol. With source routing, thesender explicitly lists the route in each packet's header, in order thatthe next-hop nodes are identified as the packet travels towards thedestination. Cached route information is used and accurate updates ofthese route caches are essential, otherwise routing loops can occur.Since the sender has to be notified each time a route is truncated, theroute maintenance phase does not support fast route reconstruction. See,also, U.S. Pat. Nos. 6,167,025; 6,034,961; and 5,987,011.

The DSR protocol appends a complete list of addresses from the source tothe destination for both upstream and downstream (i.e., bi-directional)communications. That is, each device in a DSR network knows the entirepath to another device, although this stored path may dynamicallychange.

In addition to DSR, examples of routing protocol algorithms include Adhoc on Demand Distance Vector (AODV) and proactive source routing (PSR).In a PSR routing technique, the Network Coordinator (NC) appends acomplete list of addresses from that source to the destination NetworkDevice (ND) for downstream communications (from the NC to the ND). Formulti-hop downstream communications, the receiving and repeating NDremoves its address from the list of addresses from that ND to the nextor destination ND. For upstream communications (toward the NC from theND), the originating ND appends its address in the original message toan upstream node. For multi-hop upstream communications, the receivingand repeating ND appends its address to the list of addresses from thatND to the next upstream ND or to the NC.

In contrast to wired networks, mesh-type, low rate-wireless personalarea network (LR-WPAN) wireless communication networks are intended tobe relatively low power, to be self-configuring, and to not require anycommunication infrastructure (e.g., wires) other than power sources.

Home (e.g., residential; house; apartment) monitoring, security, andautomation (control) systems are well known.

A common type of stand-alone sensor for the home is the conventionalsmoke detector, which typically employs an audible signal for alarmingand a blinking light (e.g., a LED) as a normal condition monitor. Afamily of such stand-alone sensors exists including, for example,audible door alarms.

Relatively low power, radio frequency (RF) lighting control systemsemploy wall-mounted, battery powered, RF switch “sensors”. Such a sensorsends a signal to a remote power control device, such as relay, in orderto turn one or more house lights on and off.

Unlike stand-alone devices, a low power, RF sensor device allows itssensor to be connected to a remote controller or monitor. A simpleexample of this is the automatic garage door opener. In this example,the “sensor” is a button in a car. When the button is pushed, thiscauses the garage door to open or close.

A known mechanism for associating a particular sensor with a givencontroller may involve pushing a button on the sensor while also pushinga button on the controller. This process usually requires two people.

It is known to provide a sensor system in which a plurality of sensorsare connected, either directly with wires or indirectly with RFcommunications, to a central control and monitoring device. An exampleof such a sensor system is a security system, which may include atelephone line for dial out/in communication.

One known home security system combines wired and RF sensors with acentral base station having a keypad and a display. The RF sensorstransmit to the base station. Somewhat like the handheld or keychain RFremote employed to lock/unlock a car's doors, an RF keyfob is employedto arm/disarm the system. The keyfob only transmits and sends a commandone way to the base station. The keyfob does not receive anyfeedback/confirmation, and does not receive or display any informationfrom the system. The base station does not employ a third party remotemonitoring service provider, but can be programmed to dial one or moretelephone numbers which are selected by the homeowner.

There is room for improvement in systems for the home.

SUMMARY OF THE INVENTION

These needs and others are met by the present invention, which providesa portable fob including a user input device, a display and a wirelesstransceiver communicating with the wireless transceiver of a server, inwhich the user input device and the display provide a first rotary menufor displaying sensor information and/or a second rotary menu forconfiguring a sensor.

As one aspect of the invention, a home system comprises: a serverincluding a wireless transceiver; a plurality of sensors, each of thesensors including a wireless transceiver adapted to communicate sensorinformation to the wireless transceiver of the server; and a portablefob including a user input device, a display and a wireless transceiveradapted to communicate with the wireless transceiver of the server, theuser input device and the display cooperating to provide at least one ofa first rotary menu for displaying the sensor information of the sensorsand a second rotary menu for configuring the sensors.

The at least one of the first rotary menu and the second rotary menuform a rotary menu selected by the user input device. The user inputdevice may be a rotary encoder including a selector button. The rotaryencoder may be a thumbwheel encoder including the selector button.

The first rotary menu may form the rotary menu. The thumbwheel encodermay scroll through a list of sensor names and graphical objects on therotary menu in response to the thumbwheel encoder in order to display atleast some of the sensor information.

The first rotary menu may have a top and a bottom, and the thumbwheelencoder may scroll directly between the top and the bottom of the firstrotary menu.

The second rotary menu may form the rotary menu, and the thumbwheelencoder may scroll through a list of potential sensor names on therotary menu in order to name one of the sensors in response to theselector button.

The second rotary menu may have a top and a bottom, and the thumbwheelencoder may scroll directly between the top and the bottom of the secondrotary menu.

As another aspect of the invention, a portable fob for a home systemincluding a server and a plurality of sensors comprises: a portablehousing; a wireless communication port adapted for wirelesscommunication with the server; a user input device; and a display, theuser input device and the display cooperating to provide at least one ofa first rotary menu for displaying information from the server for atleast one of the sensors and a second rotary menu for configuring atleast one of the sensors at the server.

BRIEF DESCRIPTION OF THE DRAWINGS

A full understanding of the invention can be gained from the followingdescription of the preferred embodiments when read in conjunction withthe accompanying drawings in which:

FIG. 1 is a block diagram of a home wellness system in accordance withan embodiment of the present invention.

FIG. 2A is a block diagram of the base station of FIG. 1.

FIG. 2B is a block diagram of a base station in accordance with anotherembodiment of the invention.

FIG. 3 is a block diagram of the fob of FIG. 1.

FIGS. 4A and 4B are block diagrams of two of the sensors of FIG. 1.

FIGS. 5A-5E are examples of displays used by the fob for monitoring thesensors of FIG. 1.

FIG. 5F is a simplified plan view of the fob of FIG. 1.

FIG. 5G is a block diagram of the display of the fob of FIG. 5F.

FIGS. 6A and 6B are examples of display sequences used by the fob forconfiguring the base station and sensors, respectively, of FIG. 1.

FIGS. 7A-7C are message flow diagrams showing the interaction betweenthe fob, the base station and the sensors for monitoring the sensors andsending data to the base station of FIG. 1.

FIGS. 8A-8B are message flow diagrams showing the interaction betweenone of the sensors and the base station of FIG. 1 for monitoring thatsensor.

FIGS. 9A and 9B are message flow diagrams showing the interactionbetween the fob, one of the sensors and the base station of FIG. 1 forconfiguring the fob and the sensor, respectively.

FIG. 10 is a block diagram of a PDA associated with the base station ofFIG. 1 and the corresponding display screen thereof.

FIGS. 11 and 12 are plan views of a headless base station and a portablefob in accordance with another embodiment of the invention.

FIGS. 13 and 14 are plan views of a sensor and a portable fob inaccordance with another embodiment of the invention.

FIG. 15 is an isometric view of the portable fob being mated with thesensor of FIG. 12.

FIG. 16 is a plan view of a sensor and a portable fob in accordance withanother embodiment of the invention.

FIGS. 17A-17C are plan views of a system component and a portable fob inaccordance with another embodiment of the invention.

DESCRIPTION OF THE PREFERRED EMBODIMENTS

As employed herein, a home wellness system shall expressly include, butnot be limited to, a system for monitoring and/or configuring aspects ofa home, such as, for example, home sensors.

As employed herein, the term “wireless” shall expressly include, but notbe limited to, radio frequency (RF), infrared, wireless area networks,IEEE 802.11 (e.g., 802.11a; 802.11b; 802.11g), IEEE 802.15 (e.g.,802.15.1; 802.15.3, 802.15.4), other wireless communication standards,DECT, PWT, pager, PCS, Wi-Fi, Bluetooth™, and cellular.

As employed herein, the term “handheld portable wireless communicatingdevice” shall expressly include, but not be limited to, any handheldportable communicating device having a wireless communication port(e.g., a handheld wireless device; a handheld personal computer (PC); aPersonal Digital Assistant (PDA)).

As employed herein, the term “fob” shall expressly include, but not belimited to, a handheld portable wireless communicating device; awireless network device; an object that is directly or indirectlycarried by a person; an object that is worn by a person; an object thatis placed on or attached to a household object (e.g., a refrigerator; atable); an object that is attached to or carried by a personal object(e.g., a purse; a wallet; a credit card case); a portable object; and/ora handheld object.

As employed herein, the term “user input device” shall expresslyinclude, but not be limited to, any suitable transducer (e.g., a rotaryencoder; a joystick; a micro-joystick; a touchpad, which emulates arotary encoder; a VersaPad OEM input pad marketed by InterlinkElectronics, Inc. of Camarillo, Calif.), which collects user inputthrough direct physical manipulation, with or without employing anymoving part(s), and which converts such input, either directly orindirectly through an associated processor and/or converter, into acorresponding digital form.

As employed herein, the term “rotary menu” shall expressly include, butnot be limited to, a menu or list of names, icons, graphicalidentifiers, values and/or other displayed objects, which forms acircular menu having no top and no bottom, a circular list having no topand no bottom, a menu having a top and a bottom in which the top and/orthe bottom of the menu need not be displayed at any one time, or a listhaving a top and a bottom in which the top and/or the bottom of the listneed not be displayed at any one time.

As employed herein, the term “network coordinator” (NC) shall expresslyinclude, but not be limited to, any communicating device, which operatesas the coordinator for devices wanting to join the network and/or as acentral controller in a wireless communication network.

As employed herein, the term “network device” (ND) shall expresslyinclude, but not be limited to, any communicating device (e.g., aportable wireless communicating device; a fob; a fixed wirelesscommunicating device, such as, for example, switch sensors, motionsensors or temperature sensors as employed in a wirelessly enabledsensor network), which participates in a wireless communication network,and which is not a network coordinator.

As employed herein, the term “node” includes NDs and NCs.

As employed herein, the term “headless” means without any user inputdevice and without any display device.

As employed herein, the term “server” shall expressly include, but notbe limited to, a “headless” base station; and a network coordinator.

FIG. 1 is a block diagram of a wireless home wellness system 2. Thesystem 2 includes a “headless” RF base station 4, a portable RF fob or“house key” 6, and a plurality of RF sensors, such as 8,10,12. The RFbase station 4 may include a suitable link 14 (e.g., telephone; DSL;Ethernet) to the Internet 16 and, thus, to a web server 18. The sensors8,10,12 may include, for example, the analog sensor 8, the on/offdigital detector 10, and the sensor 12. The sensors 8,10,12, basestation 4 and fob 6 all employ relatively short distance, relativelyvery low power, RF communications. These components 4,6,8,10,12 form awireless network 20 in which the node ID for each of such components isunique and preferably is stored in a suitable non-volatile memory, suchas EEPROM, on each such component.

The base station 4 (e.g., a wireless web server; a network coordinator)may collect data from the sensors 8,10,12 and “page,” or otherwise sendan RF alert message to, the fob 6 in the event that a critical statuschanges at one or more of such sensors.

The fob 6 may be employed as both a portable in-home monitor for thevarious sensors 8,10,12 and, also, as a portable configuration tool forthe base station 4 and such sensors.

The example base station 4 is headless and includes no user interface.The sensors 8,12 preferably include no user interface, although somesensors may have a status indicator (e.g., LED 116 of FIG. 4A). The userinterface functions are provided by the fob 6 as will be discussed ingreater detail, below. As shown with the sensor 12, the network 20preferably employs an adhoc, multihop capability, in which the sensors8,10,12 and the fob 6 do not have to be within range of the base station4, in order to communicate.

FIG. 2A shows the base station 4 of FIG. 1. The base station 4 includesa suitable first processor 22 (e.g., PIC® model 18F2320, marketed byMicrochip Technology Inc. of Chandler, Ariz.), having RAM memory 24 anda suitable second radio or RF processor 26 having RAM 28 and PROM 30memory. The first and second processors 22,26 communicate through asuitable serial interface (e.g., SCI; SPI) 32. The second processor 26,in turn, employs an RF transceiver (RX/TX) 34 having an external antenna36. As shown with the processor 22, the various base station componentsreceive power from a suitable AC/DC power supply 38. The first processor22 receives inputs from a timer 25 and a program switch 42 (e.g., whichdetects mating or engagement with the fob 6 of FIG. 1). The EEPROMmemory 40 is employed to store the unique ID of the base station 4 aswell as other nonvolatile information such as, for example, the uniqueIDs of other components, which are part of the wireless network 20, andother configuration related information. The second processor 26 may be,for example, a CC1010 RF Transceiver marketed by Chipcon AS of Oslo,Norway. The processor 26 incorporates a suitable microcontroller core44, the relatively very low-power RF transceiver 34, and hardware DESencryption/decryption (not shown).

FIG. 2B is a block diagram of another base station 46. The base station4 of FIG. 2A is similar to the base station 46 of FIG. 2B, except thatit also includes one or more interfaces 48,50,52 to a personal computer(PC) (not shown), a telephone line (not shown) and a network, such as anEthernet local area network (LAN) (not shown). In this example, the PICprocessor 22 communicates with a local PC through a suitable RS-232interface 48 and connector J1, with a telephone line through a suitablemodem 50 and connector J2, and with an Ethernet LAN through an Ethernetport 52 and connector J3. Hence, the modem 50 may facilitatecommunications with a remote cellular telephone, other portableelectronic device (e.g., a PDA 450 of FIG. 10) or a remote serviceprovider (not shown), and the Ethernet port 52 may providecommunications with the Internet 16 of FIG. 1 and, thus, with a remotePC or other client device (not shown).

FIG. 3 is a block diagram of the fob 6 of FIG. 1. The fob 6 includes asuitable first processor 54 (e.g., PIC) having RAM memory 56 and asuitable second radio or RF processor 58 having RAM 60 and PROM 62memory. The first and second processors 54,58 communicate throughsuitable serial interface (e.g., SCI; SPI) 64. The EEPROM memory 72 isemployed to store the unique ID of the fob 6 as well as othernonvolatile information. For example, there may be a nonvolatile storagefor icons, character/font sets and sensor labels (e.g., the base station4 sends a message indicating that an on/off sensor is ready toconfigure, and the fob 6 looks up the on/off sensor and finds apredefined list of names to choose from). This expedites a relativelyrapid interaction. The fob 6 may also employ a short term memory cache(not shown) that is used when the fob 6 is out of range of the basestation 4. This stores the list of known sensors and their last twostates. This permits the user, even if away, to review, for example,what door was open, when the fob 6 was last in range.

The second processor 58, in turn, employs an RF transceiver (RX/TX) 66having an external antenna 68. As shown with the processor 54, thevarious components of the fob 6 receive power from a battery 70. Thefirst processor 54 receives inputs from a timer 55, a suitable proximitysensor, such as a sensor/base program switch 74 (e.g., which detectsmating or engagement with one of the sensors 8,10,12 or with the basestation 4 of FIG. 1), and a user input device, such as, for example, theexemplary encoder 76 or rotary selector/switch, such as a thumbwheelencoder. The first processor 54 also sends outputs to a suitable display78 (e.g., a 120×32 LCD), one or more visual alerts, such as a redbacklight 80 (e.g., an alert is present) and a green backlight 82 (e.g.,no alert is present) for the display 78, and an alert device 84 (e.g., asuitable audible, visual or vibrating device providing, for example, asound, tone, buzzer, vibration or flashing light).

The program switch 74 may be, for example, an ESE-24 MH1T Panasonic®two-pole detector switch or a Panasonic® EVQ-11U04M one-polemicro-switch. This program switch 74 includes an external pivotable orlinear actuator (not shown), which may be toggled in one of twodirections (e.g., pivoted clockwise and counter-clockwise; in and out),in order to close one of one or two normally open contacts (not shown).Such a two-pole detector is advantageous in applications in which thefob 6 is swiped to engage the sensor 12 or base station 4, such as isdiscussed below in connection with FIGS. 11 and 12. Hence, by monitoringone of those contacts, when the fob 6 is swiped in one linear direction(e.g., without limitation, right to left in FIG. 12), the correspondingcontact is momentarily closed, without concern for overtravel of thecorresponding engagement surface (not shown). Similarly, by monitoringthe other of those contacts, when the fob 6 is swiped in the otherlinear direction (e.g., without limitation, left to right in FIG. 12),the corresponding contact is momentarily closed and another suitableaction (e.g., a diagnostic function; a suitable action in response toremoval of the fob 6; a removal of a component from the network 20; anindication to enter a different configuration or run mode) may beundertaken.

Although a physical switch 74 is disclosed, an “optical” switch (notshown) may be employed, which is activated when the fob 6, or portionthereof, “breaks” an optical beam when mating with another systemcomponent. Alternatively, any suitable device or sensor may be employedto detect that the fob 6 has engaged or is suitably proximate to anothersystem component, such as the base station 4 or sensors 8,10,12 of FIG.1.

The encoder 76 may be, for example, an AEC11BR series encoder marketedby CUI Inc. of Beaverton, Oreg. Although the encoder 76 is shown, anysuitable user input device (e.g., a combined rotary switch andpushbutton; touch pad; joystick button) may be employed. Although thealert device 84 is shown, any suitable annunciator (e.g., an audiblegenerator to generate one or more audible tones to alert the user of oneor more corresponding status changes; a vibrational generator to alertthe user by sense of feel; a visual indicator, such as, for example, anLED indicator to alert the user of a corresponding status change) may beemployed. The display 78 preferably provides both streaming alerts tothe user as well as optional information messages.

FIGS. 4A and 4B are block diagrams of the on/off digital (discrete)sensor 10 and the analog sensor 8, respectively, of FIG. 1. Each of thesensors 8,10 includes an RF transceiver (RF RX/TX) 86 having an externalantenna 88, a battery 90 for powering the various sensor components, asuitable processor, such as a microcontroller (μC) 92 or 93 having RAM94, ROM 96, a timer 98 (e.g., in order to provide, for example, aperiodic wake-up of the corresponding μC 92 or 93, in order toperiodically send sensor status information back to the base station 4of FIG. 1) and other memory (e.g., EEPROM 100 including the unique ID102 of the component which is stored therein during manufacturing), anda sensor program switch 104 for mating with the fob program switch 74 ofFIG. 3. The on/off digital (discrete) sensor 10 includes a physicaldiscrete input interface 106 (e.g., an on/off detector; an open/closeddetector; a water detector; a motion detector) with the μC 92 employinga discrete input 108, while the analog sensor 8 includes a physicalanalog input interface 110 (e.g., temperature sensor having an analogoutput; a light sensor or photo-sensor having an analog output) with theμC 93 employing an analog input 112 and a correspondinganalog-to-digital converter (ADC) 114.

The sensor 10 of FIG. 4A includes a suitable indicator, such as an LED116, to output the status of the physical discrete input interface 106(e.g., LED illuminated for on; LED non-illuminated for off). The sensor8 of FIG. 4B does not include an indicator. It will be appreciated,however, that the sensor 10 need not employ an indicator and that thesensor 8 may employ an indicator (e.g., to show that the battery 90 isOK; to show that the analog value from the ADC 114 is within anacceptable range of values).

FIGS. 5A-5E are example displays 120,122,124,126,128 employed by the fob6 for monitoring various sensors, such as 8,10,12 of FIG. 1. Inaccordance with an important aspect of this embodiment, the fob display78 of FIG. 3 provides a rotary menu 130 of information 131, which thebase station 4 monitors from the various sensors. As shown in FIG. 5A,such sensors might be associated with various sensor names such as, forexample, Basement, Garage Door, Kitchen Wi(ndow), Living Room, MasterBed(room), Stereo Sys(stem) and Television, wherein the parentheticalportion of those names is truncated for display in this example. Also,in this example, the system message region 132 of the fob display 78shows an overall system/connectivity status of the fob 6 being “Updated:5 minutes ago” by the base station 4. If, for example, the informationis too long to fit in the region 132, then this display region cyclesthrough messages or auto-scrolls from right to left (e.g., in tickertapestyle). The content region 134 of the fob display 78 shows three of thesensor names (e.g., Basement, Garage Door, Kitchen Wi(ndow)), while theremaining four names 136 (e.g., Living Room, Master Bed(room), StereoSys(tem) and Television), in this example, are available for displayfrom the rotary menu 130 in fob PIC processor RAM memory 56 (FIG. 3) byemploying the rotary knob 138 as will be described. Thus, theinformation 131 includes both information for the content region 134 andinformation for the other names 136.

The display content region 134 includes sensor information from the mostrecent update from the base station 4. For example, the system messageregion 132 of FIG. 5B shows that the fob 6 is now “Getting Update . . .,” FIG. 5C shows that “All Systems: Ok . . . Just Up(dated)” and FIG. 5Dshows that the fob 6 was just “Updated: 5 seconds ago” as measured fromthe current time.

It will be appreciated that the names in the rotary menu 130 and in theinformation 131 may be displayed in a wide range of orders. For example,the names may be presented in alphabetical order, in the order that thecorresponding sensors 8,10,12 were configured as part of the home system2 of FIG. 1, in an order reflecting sensor location in such home system,or in an order prioritized by severity. For example, alerts havepriority over status information. As a further example, the nature ofone sensor (e.g., smoke; fire) and its state (e.g., smoke detected; firedetected) may have a higher severity than that of another sensor (e.g.,bedroom lights) and its state (e.g., off).

The various icons 140 of FIG. 5A reflect the actual state of thecorresponding sensors. For example, the outline of the water drop icon142 shows that the corresponding Basement sensor (not shown) has notdetected water, the open door icon 144 of the corresponding Garage Doorsensor (not shown) shows that the corresponding door (not shown) isopen, the lit bulb icon 146 (FIG. 5B) of the Master Bed(room) sensor(not shown) shows that the corresponding light (not shown) is on, andthe non-lit bulb icon 148 of the Stereo Sys(tem) sensor (not shown)shows that the corresponding system (not shown) is off.

The sensor names in the rotary menu 130 are scrolled by the rotary knob138. A sufficient clockwise rotation scrolls the names upward (or thedisplayed menu 130 downward), for example, two positions, from FIG. 5Ato FIG. 5B, such that the names and icons for Kitchen Wi(ndow), LivingRoom and Master Bed(room) are displayed. Similarly, another sufficientclockwise rotation scrolls the names upward, for example, two positions,from FIG. 5B to FIG. 5C, such that the names and icons for MasterBed(room), Stereo Sys(stem) and Television are displayed. Of course,different amounts of rotation of the rotary knob 138 scroll the nameszero, one, two, three or more positions, and a sufficientcounter-clockwise rotation (not shown) scrolls the names downward one ormore positions.

FIGS. 5F and 5G illustrate the user interface of the fob 6 of FIG. 1.This user interface is preferably intuitive, consistent, andpredictable, in which the various “screens” (e.g., FIGS. 5A-5E and6A-6B) in the interface follow a predictable, interaction “physics.” Therotating knob 138 on the fob 6 is employed, for example, to select andfollow links, which allow the user to navigate from screen to screen. Inparticular, the rotating knob 138 is used to scroll through information,and highlight and follow links displayed on the display 78.

By rotating the knob 138 clockwise, this scrolls the rotating menu 130(e.g., as was discussed above in connection with FIGS. 5A-5C).Alternatively, the knob 138 may move the pointer or cursor 150 downwardby counter-clockwise rotation under certain user interface conditions asdetermined by the fob PIC processor 54. Alternatively, the knob 138 mayhighlight any links displayed on the screen, in sequence. Similarly, byrotating the knob 138 counter-clockwise, this scrolls the rotary menu130 downward and/or highlights the links in the opposite order.

Pushing the knob 138 at central position 152 functions like pressing themouse button on a desktop computer. Then, the selected link is typicallyfollowed to a new screen. Alternatively, some selected links change justa section of the current screen and/or “unfold” more of the largervirtual scroll. As another alternative, the selected link may perform anoperation, such as, for example, resetting a maximum value.

Preferably, navigation is never deeper than one level beyond a homescreen (e.g., from FIG. 5C to or from FIG. 5D). When the user takessteps to configure a sensor (e.g., by mating the fob 6 with the sensor12 of FIG. 1), the fob 6 automatically displays the screen 154 of FIG.6B. Similarly, when the user completes the sensor configuration (e.g.,by selecting “Done/Exit Training?” 156 of screen 158 of FIG. 6B), thescreen of FIG. 5A, for example, is automatically re-displayed by the fob6.

Holding the rotary knob 138 in for a predetermined time (e.g., overabout one second) anywhere or anytime during the interaction flowautomatically returns the user to the home screen.

FIG. 5G shows that the fob display 78 includes two parts: the systemmessage region 132, and the content region 134. The system messageregion 132 displays overall system/connectivity status as well ascontext specific hints. For example, the system message region 132 mightdisplay that the fob 6 was “Last Updated: 20 minutes ago” by the basestation 4, was “Last Updated: 5 minutes ago” by the base station 4, iscurrently “Getting Update . . . ” from the base station 4, is “Out ofRange” of the base station 4, or that the user should “<press button fordetails>”.

As another example, the content region 134 is the largest section of thefob display 78 and is devoted to the display of detailed information(e.g., in the form of relatively large animated icons and text) aboutthe system and elements therein. Often, this screen acts as a “window”into a larger virtual scroll.

The rotary menu 130 of FIG. 5A may be implemented in various manners.Two examples follow.

EXAMPLE 1

In this example, Basement is at the top of the list of information 131and Television is at the bottom of the list, with no wrapping fromTelevision back to Basement being permitted. Also, in this example, thedownward arrow 160 of FIG. 5A indicates that Basement is at the top ofthe list, the upward and downward arrows 162 of FIG. 5B indicate thatthe three names are not at the top or the bottom of the list, and theline and upward arrow 164 of FIG. 5C indicates that Television is at thebottom of the list.

EXAMPLE 2

Alternatively, as shown in FIG. 5E, Television is followed by Basementin the content region 134 if there is further clockwise rotation of therotary knob 138, thereby providing a list or menu that wraps. Similarly,if the rotary knob 138 is then rotated slightly counter-clockwise, thenames displayed would include: Stereo Sys(tem), Television and Basement.

As shown in FIG. 5C, the Master Bed(room) name is highlighted by thecursor icon 166 and, when the knob 138 (FIG. 5A) is pushed, the laststatus information from the corresponding sensor (not shown) isdisplayed below that name. In this example, the sensor has twoattributes, Lights 168 and Battery 170, and the states of thoseattributes, On 172 and Ok 174, respectively, are also displayed.Generally, sensors include at least the corresponding analog or digitalstate being monitored, and may also include health information (e.g.,battery level; not responding; intermittent).

FIGS. 6A and 6B show sequences of displays employed by the fob 6 forconfiguring the base station 4 and the sensors 8,10,12, respectively, ofFIG. 1. FIG. 6A shows a set of fob display screens that the user employsto configure the fob 6 and base station 4. First, screen 180 thanks theuser for choosing the system 2. This is followed by screen 182, whichprompts the user, at 183, to press the knob 138 of FIG. 5A to begin. Thenext two screens 184,186 respectively instruct the user to power (e.g.,plug in an AC power cord (not shown)) the base station 4 and prompt theuser, at 187, to press the knob 138 to continue. The next two screens188,190 graphically inform the user to insert the fob 6 into the basestation 4. Those screens 188,190 are preferably repeated until the fobPIC processor 54 detects that the sensor/base program switch 74 of FIG.3 is active or closed. When that switch 74 closes in response to the fob6 being suitably mated with the base station 4, the screen 190transitions, at 191, to the screen 192, which informs the user, at 193,that the fob 6 is gathering (or exchanging) information with the basestation 4 (e.g., the ID of the fob 6 is sent to the base station 4 viathe RF transceivers over the wireless network 20, the ID of the basestation 4 is sent to the fob 6, and other pertinent data is providedfrom the base station 4 to the fob 6) by exchanging a series of messages(not shown). Next, the user is informed by screen 194 that the basestation 4 has been identified, by screen 196 that the system 2 is beingactivated, and by screen 198 that the base station 4 is ready. Then,screen 200 prompts the user, at 201, to press the knob 138 to continue.In response to that action, screen 202 informs the user that the fob 6is ready and, thus, that the fob RAM memory 60 (FIG. 3) includes, forexample, the particular node ID of the base station 4 and that both thefob 6 and base station 4 are part of the system 2. Finally, screen 204prompts the user, at 205, to press the knob 138 to continue. When thataction occurs, execution resumes with screen 206 of FIG. 6B.

At screen 206 of FIG. 6B, the user is instructed to insert the fob 6into a sensor (e.g., a non-configured sensor 207) in order to add it tothe system 2 of FIG. 1. In summary, when one of the sensors 8,10,12 iskeyed in this manner, the fob 6 begins gathering correspondinginformation and, then, reports the success to the user. As discussedbelow, the fob 6 provides the ability to customize the sensor 207, withthe status bar 132 cycling through two messages “<dial to highlight . .. >” and “press to select>”. Following the screen 206, the screen 154reports that the fob 6 is gathering information. This is possible,because there are two, and only two, components in the system 2 (e.g.,the fob 6 and the particular sensor 207 (or the base station 4), whichare mated and which have their corresponding switches 74,104 closed atany one time). As discussed below in connection with FIG. 9B, when thesensor switch 104 is activated by mating with the fob 6, the sensor 207sends a request to the base station 4 to join the network 20(attempt_network_discovery). The fob program switch 74 is also activated(e.g., simultaneously) by mating with the sensor 207, and the fob 6 alsosends a “program sensor” message to the base station 4. By receivingthis “confirmation” message from the fob 6, the base station 4 knows toaccept this sensor 207 to the network 20, and sends anwk_connect_confirm message. Next, screen 208 reports the type of sensor(e.g., an Open-Close Sensor 209 in this example). Then, screen 210reports that the sensor 207 is identified and screen 212 removes the“<gathering info . . . >” message 213 from the status bar 132.

Next, the screens 214 and 216 prompt the user to “<dial to highlight . .. >” and “<press to select>” one of the three displayed actions:“Customize sensor?”, “Done/Exit Training?” And “Remove Sensor?”. If theuser highlights and presses (e.g., employing the rotary knob 138 of FIG.5A) “Customize sensor?” at screen 218, then screen 220 is displayed,which confirms that the sensor 207 is an “Open-Close Sensor” 221 andlists in the lower rotary (configuration) menu 222 the possible names ofthat sensor. In this example, there are two possible names shown, whichare based upon the possible locations for such a sensor: Living R(O)mWindow and Front Door, wherein the parenthetical portion of those namesis truncated for display in this example. Also, in this example, theremay be one, three or more names and the display operation of the rotary(configuration) menu 222 may mimic the display operation of the rotary(monitoring) menu 223 of FIG. 5E. Next, after the user highlights one ofthe names, such as Front Door 225, the screen 224 prompts the user topress the knob 138 of FIG. 5A to select that name. Next, after the userselects the name, the screen 226 displays the name, Front Door 227, inthe system message region 132, and prompts the user to select one of thesensor awareness levels, for example, “Silent awareness?”, “Alert me ifopened?” and “Alert me if closed?”. Although, zero, one, two, three ormore awareness levels may be employed for a particular sensor, in thisexample, “Silent Awareness?” means that the audible buzzer 84 (FIG. 3)of the fob 6 is inactive regardless of the state of that sensor.Otherwise, the user can select that an audible alert as determined bythe base station 4 be sounded if that configured sensor is opened or ifsuch sensor is closed. Next, at screen 228, the user, in this example,selects “Silent awareness?”, which causes the screen 216 to beredisplayed. At that point, if the user highlights and selects the“Done/Exit Training?” option 156, then the newly entered information forthe sensor 207 is transferred to the base station 4. Alternatively, ifthe user highlights and selects the “Remove sensor?” option 230, andregardless whether the sensor 207 was previously added, that informationfor such sensor is transferred to the base station 4, in order to removethe sensor 207 from the system 2. Finally, if the user highlights andselects the “Customize sensor?” option 230, screen 218 is redisplayed,no information is sent to the base station 4, and the user is promptedto re-enter the information to customize the sensor 207.

FIGS. 7A, 7B and 7C are message flow diagrams 252, 254 and 256,respectively, showing various messages between the base station 4 andthe fob 6 for monitoring the sensors 8,10,12 of FIG. 1 and for sendingfob data to such base station. FIG. 7A shows that the fob 6 requests andreceives information from the base station 4. Preferably, those requests(only one request is shown) are initiated at regular (e.g., periodic)intervals. FIG. 7B shows that the base station 4 may also send a messageto the fob 6 in response to a state change of one of the sensors8,10,12. In this example, the fob 6 is out of range of the base station4. FIG. 7C shows that the fob 6 sends fob data 258 to the base station4. As shown in FIGS. 2A-2B, 3 and 7A-7C, the base station 4 includesboth a PIC processor 22 and an RF processor 26, and the fob 6 includesboth a PIC processor 54 and an RF processor 58. It will be appreciated,however, that such components may alternatively employ one or moresuitable processors.

As shown in FIG. 7A, the fob 6 periodically requests and receivesinformation from the base station 4. The message sequence 260 is alsodiscussed below in connection with FIG. 9B. At the end of that sequence260, the fob PIC processor 54 sends a SLEEP_request( ) 262 to the fob RFprocessor 58. Then, after a suitable sleep interval to conserve batterypower (e.g., one minute), the fob PIC processor 54 is woken by the fobtimer 55 of FIG. 3, and the fob PIC processor 54 sends a WAKEUP_request() message 264 to the fob RF processor 58. In turn, the message sequence260 is executed to refresh the local fob data table 266 with the mostrecent available information from base station 4 concerning the sensors8,10,12.

As part of the sequence 260, the fob PIC processor 54 sends aPICDATA_request(rqst_updates) message 268 to the fob RF processor 58,which receives that message 268 and responsively sends aData(reqst_updates) RF message 270 to the base RF processor 26. Uponreceipt of the RF message 270, the base RF processor 26 sends anAcknowledgement(SUCCESS)RF message 272 back to the fob RF processor 58and sends a PICDATA_indication(rqst_updates) message 274 to the base PICprocessor 22. The data requested by this message 274 may include, forexample, profile and state information from one or more components, suchas the sensors 8,10,12. Here, the fob 6 is requesting an update from thebase PIC processor 22 for data from all of the sensors 8,10,12,including any newly added sensor (e.g., sensor 207 of FIG. 6B), in viewof that state change (i.e., there is new data from the newly addedsensor 207). Responsive to receiving the Acknowledgement(SUCCESS) RFmessage 272, the fob RF processor 58 sends a PICDATA_confirm(SENT)message 276 to the fob PIC processor 54. Responsive to receiving thePICDATA_indication(rqst_updates) message 274, the base PIC processor 22sends a PICDATA_request(updates) message 278 to the base RF processor26, which receives that message 278 and responsively sends aData(updates) RF message 280 to the fob RF processor 58.

After receiving the Data(updates) RF message 280, the fob RF processor58 sends an Acknowledgement(SUCCESS)RF message 282 back to the base RFprocessor 26 and sends a PICDATA_indication(updates) message 286,including the requested sensor update data, to the fob PIC processor 54,which updates its local data table 266. Then, if there is no activity ofthe fob thumbwheel 138 of FIG. 5F, or if no alert is received from thebase station 4, then the fob PIC processor 54 sends a SLEEP_request( )message 262 to the fob RF processor 58 and both fob processors 54,58enter a low power_mode( ) 288,290, respectively.

After receiving the Acknowledgement(SUCCESS)RF message 282, the base RFprocessor 26 sends a PIC_DATA_confirm(SENT) message 284 back to the basePIC processor 22. Following the message sequence 260, the fob timer 55awakens the fob PIC processor 54, at 291, which sends the message 264 tothe fob RF processor 58, in order to periodically repeat the messagesequence 260.

FIG. 7B shows an alert message sequence from the base station 4 to thefob 6, in which the fob 6 is out of range of the base station 4. First,at 293, the base station PIC processor 22 sends aPIC_DATA_request(alert) message 292 to the base station RF processor 26.In response, that processor 26 sends a Data(alert) RF message 294 to thefob RF processor 58. In this example, any RF message sent by the basestation 4 while the fob 6 is out of range (or in low power mode) will belost. After a suitable time out period, the base station RF processor 26detects the non-response by the fob 6 and responsively sends aPIC_DATA_confirm(OUT_OF_RANGE) message 296 back to the base station PICprocessor 22. A successful version of this message sequence 254 isdiscussed below in connection with FIG. 9B.

In FIG. 7C, at 297, the fob PIC processor 54 sends aPICDATA_request(data) message 298 to the fob RF processor 58. Next, thefob RF processor 58 sends a Data(data) RF message 299 including the fobdata 258 to the base station RF processor 26. In response, the basestation RF processor 26 sends an Acknowledgement(SUCCESS)RF message 300to the fob RF processor 58. Finally, the fob RF processor 58 sends aPICDATA_confirm(SENT) message 302 to the fob PIC processor 54.

FIGS. 8A and 8B are message flow diagrams 310,312 showing variousmessages between one of the sensors 8,10,12 and the base station 4 ofFIG. 1 for monitoring that sensor. FIG. 8A shows that the sensor sendsstate information to the base station 4 at regular (e.g., periodic)intervals. FIG. 8B shows that the sensor also sends state information tothe base station 4 in response to sensor state changes. The sensor timer98 of FIGS. 4A and 4B preferably establishes the regular interval,sensor_heartbeat_interval 314 of FIGS. 8A-8B (e.g., without limitation,once per minute; once per hour; once per day; any suitable time period),for that particular sensor, such as 8,10,12. It will be appreciated thatthe regular intervals for the various sensors 8,10,12 may be the same ormay be different depending upon the desired update interval for eachparticular sensor.

In FIG. 8A, after the expiration of the sensor_heartbeat_interval 314,the sensor, such as 10, wakes up (wake_up( )) at 316. Next, the sensor10 sends a Data(state_information) RF message 318 to the base station RFprocessor 26, and that RF processor 26 responsively sends anAcknowledgement(SUCCESS)RF message 320 back to the sensor 10. Responsiveto receiving that message 320, the sensor 10 enters a low_power_mode( )324 (e.g., in order to conserve power of the sensor battery 90 of FIG.4B). Also, responsive to sending that message 320, the base station RFprocessor 26 sends a PICDATA_indication(state) message 322 to the basestation PIC processor 22. Both of the Data(state_information) RF message318 and the PICDATA_indication(state) message 322 convey the state ofthe sensor 10 (e.g., sensor on/off; sensor battery OK/low).

The low_power_mode( ) 324 is maintained until one of two events occurs.As was previously discussed, after the expiration of thesensor_heartbeat_interval 314, the sensor 10 wakes up at 316.Alternatively, as shown in FIG. 8B, the sensor 10 wakes up (wake_up( )326) in response to a state change (e.g., the sensor 10 detects an on tooff transition or an off to on transition of the sensor discrete input106 of FIG. 4A). Next, the sensor 10 sends a Data(state_information) RFmessage 328 to the base station RF processor 26, and that RF processor26 responsively sends an Acknowledgement(SUCCESS)RF message 330 back tothe sensor 10. Responsive to receiving that message 330, the sensor 10enters a low_power_mode( ) 332. After the expiration of thesensor_heartbeat_interval 314, the sensor 10 wakes up at 316 of FIG. 8A.Next, at 333, the base station RF processor 26 responsively sends aPICDATA_indication(state) message 334 to the base station PIC processor22. Both of the Data(state_information) RF message 328 and thePICDATA_indication(state) message 334 convey the state of the sensor 10.Responsive to receiving that message 334, the base station PIC processor22 sends a PICDATA_request(alert) message 336 to the base station RFprocessor 26. Such an alert is sent whenever there is any sensor statechange. Finally, the base station RF processor 26 sends a Data(alert) RFmessage 338 to the fob RF processor 58. The response by that processor58 and the subsequent activity by the fob 6 are discussed, below, inconnection with a sensor joining the network 20 of FIG. 1 and FIG. 9B,which shows the procedure and messages for the state update.

FIGS. 9A and 9B are message flow diagrams 350,352 showing theinteraction between the fob 6, one sensor, such as 10, and the basestation 4 of FIG. 1 for configuring that fob and sensor. In FIG. 9A,after the four processors 54,58,26,22 complete respective power_on( )initialization 354,356,358,360, the fob 6 may join the network 20 of thebase station 4. The sensor 10 also initiates power_on( ) initialization362.

Initially, in response to the screens 188,190 of FIG. 6A, the userundertakes a FOB_swipe( ) 364 of the fob 6 with the base station 4. Inview of the screens 188,190, the fob PIC processor 54 knows, at thispoint, that the mated component is the base station 4. The fob PICprocessor 54 detects the closure of the sensor/base program switch 74 ofFIG. 3 and responsively sends a JOIN_request(NetworkDevice) message 366to the fob RF processor 58, which responsively executes aninitialize_comm_stack( ) routine 368. This routine 368 initializes thecommunication stack of that processor, which provides suitable softwareservices for communication from one RF component (e.g., the fob 6) toanother RF component (e.g., the base station 4). Next, the fob RFprocessor 58 sends an attempt_nwk_discovery( ) RF message 370 to thebase RF processor 26, which may or may not be ready for that message.Only after the base station 4 has successfully initialized, will thesediscovery attempts of the fob 6 be successful. At that point, the fob 6can transmit its profile 363 to the base station 4.

When the base PIC processor 22 is notified, as a result of theFOB_swipe( ) 364 of the fob 6 with the base station 4, of the closure ofthe program switch 42 of FIG. 2A, it responsively sends aJOIN_request(NetworkCoordinator) 371 message to the base RF processor26, which responsively executes an initialize_comm_stack( ) routine 372.As a result, the base communication stack is initialized and the base RFprocessor 26 is ready to accept requests from other components to jointhe network 20 of FIG. 1. When the routine 372 concludes, the base RFprocessor 26 sends a JOIN_confirm(SUCCESS) message 374 back to the basePIC processor 22. Therefore, the base RF processor 26 is now ready toaccept requests from other components (e.g., the sensor 10; the fob 6)to join the network 20.

Although the first attempt_nwk_discovery( ) RF message 370 to the baseRF processor 26 was ignored, since the routine 372 had not yetconcluded, a second or subsequent attempt_nwk_discovery( ) RF message,such as 376, is sent to and is received by the base RF processor 26.That processor 26 receives the message 376 and responds with anwk_connect_confirm( ) RF message 378 back to the fob RF processor 58.When the message 378 is received, the fob RF processor 58 sends aJOIN_confirm(SUCCESS) message 380 back to the base PIC processor 54.

The profile 363, for a component such as the fob 6, includes suitablecomponent identification information, which, for example, identifies thecomponent as a fob and provides the node ID and any attributes thereof.The profile 363 is transmitted to the base RF processor 26 after the fobRF processor 58 has joined the network 20 of FIG. 1. In this regard, thefob RF processor 58 may periodically attempt that action as shown by theexample sequence of two attempt_nwk_discovery( ) RF messages 370,376 tothe base RF processor 26. It will be appreciated that one or more ofsuch attempts are employed. Also, such attempts at discovery may beemployed after power is on and independent of the engagement of the fob6 with the base station 4.

At 381, the fob 6 can transmit its profile 363 to the base station 4.The fob PIC processor 54 sends a PICDATA_request(profile) message 382 tothe fob RF processor 58, which responsively sends aDATA(profile_information) RF message 384. That message 384 is receivedby the base RF processor 26. In response, that processor 26 sends anAcknowledgement(SUCCESS)RF message 386 back to the fob RF processor 58.Upon receipt of that message 386 by the fob RF processor 58, it sends aPICDATA_confirm(SENT) message 388 back to the fob PIC processor 54.

After sending the Acknowledgement(SUCCESS)RF message 386, the base RFprocessor 26 sends a PICDATA_indication(profile) message 390 to the basePIC processor 22. Upon receipt of the message 390, the base PICprocessor 22 sends a PICDATA_request(profile_confirm) message 392 to thebase RF processor 26 and, also, stores the profile 363 for the fob 6 inan internal table 393 of components, which have been added to thenetwork 20. Upon receipt of the message 392, the base RF processor 26sends a DATA(profile_confirm) RF message 394 to the fob RF processor 58.Upon receipt of that message 394 by the fob RF processor 58, it sends anAcknowledgement(SUCCESS)RF message 396 back to the base RF processor 26and sends a PICDATA_indication(profile_confirm) message 400 back to thefob PIC processor 54. In response to receipt of that message 400, thefob PIC processor 54 displays the fob acceptance screen 202 (“Key isready.”) of FIG. 6A to the user. Upon receipt of the RF message 396, thebase RF processor 26 sends a PICDATA_confirm(SENT) message 398 to thebase PIC processor 22. Finally, at 401, the fob PIC processor 54 sends aSLEEP_request( ) message 402 to the fob RF processor 58 and both fobprocessors 54,58 enter a low_power_mode( ) 404,406, respectively.

Referring to FIG. 9B, in order to join one of the sensors, such as 10,to the network 20 of FIG. 1, the user suitably mates the fob 6 with thatsensor. In response, the fob PIC processor 54 detects the sensor/basestation program switch 74 of FIG. 3 being closed. In view of the screen206 of FIG. 6B, the fob 6 knows, at this point, that the mated componentis a sensor. Following the FOB_switch_pressed( ) routine 412, the fobPIC processor 54 send a WAKEUP_request( ) message 414 to the fob RFprocessor 58.

Similar to the fob RF processor's RF messages 370,376, the sensor 10periodically sends RF messages, such as the attempt_nwk_discovery( ) RFmessage 420, to the base RF processor 26. Otherwise, the sensor 10 goesto a low power mode, such as 427, if the network discovery attempts areunsuccessful. The sensor 10 then retries (not shown) such networkdiscovery attempts after a suitable time in low power mode.

At 415, after sending the wakeup message 414, the fob PIC processor 54sends a PICDATA_request(SensorJoining) message 416 to the fob RFprocessor 58, which, in turn, sends a DATA(SensorJoining) RF message 418to the base RF processor 26. The physical action of the FOB_swipe( ) 410also causes the sensor 10 to detect the closure of the sensor programswitch 104 of FIG. 4A. Preferably, that action triggers the first RFmessage 420.

In view of the two RF messages 418,420 to the base RF processor 26, itresponsively sends a nwk_connect_confirm( ) RF message 422 back to thesensor 10. Upon receipt of that RF message 422, the sensor 10 sends aDATA(profile_information) RF message 424 back to the base RF processor26. That RF message 424 includes the sensor profile 425, which includessuitable component identification information, such as type of component(e.g., sensor), the type of sensor (e.g., on/off; one input; batterypowered), the node ID and any suitable attributes of the sensor 10. Uponreceipt of that RF message 424, the base RF processor 26 sends thesensor 10 an Acknowledgment(SUCCESS)RF message 426. Next, the base RFprocessor 26 sends the base PIC processor 22 aPICDATA_indication(profile) message 428, including the sensor profile425. The base PIC processor 22 receives that message 428 and stores theprofile 425 in the table 430. The base PIC processor 22 also sends thebase RF processor 26 a PICDATA_request(alert) message 432, whichindicates that a new sensor 10 has been added to network 20. As will beseen, this message 432 is ultimately communicated to the fob 6, whichwill, then, need to responsively request data associated with the newlyadded sensor 10.

After receiving the Acknowledgment(SUCCESS)RF message 426, the sensor 10enters the low_power_mode( ) 427. In turn, after a suitablesensor_heartbeat_interval 429, the sensor 10 wakes up as was discussedabove in connection with FIG. 8A.

Upon receipt of the PICDATA_request(alert) message 432, the base RFprocessor 26 sends a Data(alert) RF message 434 to the fob RF processor58, which receives that RF message 434 and responsively sends anAcknowledgement(SUCCESS)RF message 436 back to the base RF processor 26.Upon receipt of the RF message 436, the base RF processor 26 sends aPICDATA_confirm(SENT) message 438 to the base PIC processor 22. Then,after the fob RF processor 58 sends the RF message 436, it sends aPICDATA_indication(alert) message 440 to the fob PIC processor 54. Next,the message sequence 260 of FIG. 7A is executed to provide sensorinformation for the newly added sensor 10 to the fob 6.

As part of the sensor profile 425, the sensor 10 provides, for example,a node ID, a network address and/or a unique sensor serial number. Aspart of the messages 416,418, the fob 6 provides a graphical identifier(e.g., a label; sensor name; sensor attribute) associated with theconfiguration of the sensor (e.g., screen 224 of FIG. 6B provides thename “Front Door” 225 for the sensor being configured).

FIG. 10 shows a PDA 450 associated with the base station 4 of FIG. 1 andthe corresponding display screen 452 thereof. The base station 4communicates with the PDA 450 through RF, cellular or other wirelesscommunications 454 from the web server 18 of FIG. 1. Although a PDA 450is shown, the base station 4 may communicate, for example, with the fob6, a PC (e.g., palm top; lap top) (not shown), the Internet 16 of FIG.1, or a web-enabled telephone (not shown).

The display screen 452 preferably provides a suitable menu 456 (e.g.,including status, calendar, setup and sensor information). The“at-a-glance” display also communicates critical information about the“wellness” (e.g., “health”) of the home. That information may includeinformation obtained from the sensors 8,10,12 (e.g., mail, temperature,alarm, lights, fire, electric, security, heat, air conditioning (AC),water, and home computer system or wireless LAN firewall).

EXAMPLE 3

The base station 4 may provide remote status and alerts directly to thehomeowner or user through, for example, telephone, cellular telephone,pager, e-mail or AOL Instant Messenger messages, remote fob, facsimile,any suitable messaging mechanism, or the Internet 16 of FIG. 1 regardingvarious home conditions, functions and/or utilities.

EXAMPLE 4

Examples of the types of sensors 12 of FIG. 1 include water leaks; poweroutages; abnormal temperatures (e.g., home; refrigerator; furnace; airconditioner; heat pump); motion (e.g., child; pet; elderly person; wildanimal); alarm (e.g., open or ajar; door; window; cabinet); appliance on(e.g., iron; television; coffee pot); sound (e.g., smoke alarm; intruderalert); status of detached garage; tremor (e.g., earthquake); odor(e.g., natural gas); pressure (e.g., package delivered to front doormat); manual request (e.g., a button is pressed on a “nameable” sensor,such as, for example, “bring takeout” or “out of milk”). The sensor 12may include, for example, conventional security devices (e.g., motion;door status; window status; smoke; fire; heat; gas (e.g., carbonmonoxide, natural gas); alarm) and home condition monitors (e.g.,moisture; temperature; power; energy (e.g., natural gas; water;electricity; power)).

EXAMPLE 5

Relatively short range wireless communications (e.g., withoutlimitation, RF) may be employed between the sensors 8,10,12 (and the fob6) and the base station 4.

EXAMPLE 6

The base station 4 may employ relatively long range communications(e.g., a homeowner's existing land telephone line; DSL modem) in orderto reach the owner remotely (e.g., cellular telephone; pager; Internet).

EXAMPLE 7

Locations without a land telephone line may employ a suitable cellularcontrol channel (e.g., like an asset management system) in order toconvey sensor information remotely.

EXAMPLE 8

The home wireless communications may be self-configuring in order that atypical homeowner can readily install and easily use the system 2 andsensors 8,10,12 of FIG. 1 with relatively minimal setup.

EXAMPLE 9

Bi-directional wireless communications may be employed between thesensors 8,10,12 (and the fob 6) and the base station 4, in order toassure message receipt/acknowledgment.

EXAMPLE 10

The base station 4 may allow remote control by the fob 6 of selectedhouse functions (e.g., changing the temperature at a thermostat (notshown)).

EXAMPLE 11

The fob 6 may provide a personal dashboard (e.g., status indicators) ofthe home in order to provide at-a-glance status and awareness of varioushome conditions.

EXAMPLE 12

The system 2 may provide only relatively short range, wirelesscommunications between the sensors 8,10,12 (and the fob 6) and the basestation 4.

EXAMPLE 13

The system 2 may provide relatively short range, wireless communicationsbetween the sensors 8,10,12 (and the fob 6) and the base station 4, andrelatively long range communications to the owner through a remote fob(e.g., the PDA 450 of FIG. 10). For example, the base station 4 maycommunicate with a cell (data) phone (not shown) or a pager (not shown)as a remote user interface.

EXAMPLE 14

The system of Example 12 may also provide relatively long rangecommunications to the owner through a remote fob (e.g., the PDA 450 ofFIG. 10).

EXAMPLE 15

The system 2 may provide a mechanism to allow the owner through a localor remote fob to forward or send an alert to a service contractor (notshown) or another party.

EXAMPLE 16

The system 2 may be associated with a service provider, which takescalls from the owner or from the base station 4 and contacts “certified”(e.g., trustworthy) contractors.

EXAMPLE 17

The system 2 may be associated with a service provider, which takescalls from the owner or from the base station 4 and respondsaccordingly.

EXAMPLE 18

The system of Examples 12-15 may not require a service contract (e.g.,fees) with a security company.

EXAMPLE 19

The system of Examples 12-18 may address the level of programmabilityand customization available (e.g., in order to create unique sensornames; script simple logic). The communication interfaces 48,50,52 onthe base station 4 may be employed to allow the user to createpersonalized names for sensors by entering them at a PC or through anInternet browser.

EXAMPLE 20

The fob 6 is preferably portable and relative small. The fob 6, whichsupports wireless communications, enables the base station 4 to be“headless”. In this manner, the user may employ the fob 6 as a userinterface to the system 2 wherever the user wants to employ it (e.g.,carried; worn; attached to a refrigerator; placed on a table; placed ona nightstand) because it is wireless. The fob 6 provides the user orowner with awareness by exception, and provides peace of mind (i.e.,everything is ok in the home).

The fob configuration procedure differs from that of known home productsand systems in that it provides a single button 152 and a dial or rotaryselector 138 (FIG. 5F), in order to select from a predetermined list ofsensor names and attributes based on, for example, the location and typeof component being configured (e.g., context aware). The fob 6 combinesthe low cost of memory, short-range wireless communication, and aplurality of configuration definitions or names (see, for example,Examples 21-27, below). This configuration procedure preferably employsa successively layered interaction protocol (e.g., first time users willonly see the top “layer” of interaction choices, such as add a sensor orname a sensor, but once the user has experienced and learned theinteraction physics, then they will discover deeper avenues ofconfiguration, such as clicking on a sensor name expands the list toshow more details) in order to allow for both first time and experienceduser access to typical or most likely system tasks.

EXAMPLE 21

Non-limiting examples of types of the sensors 8,10,12 of FIG. 1 includeopen/close devices, on/off devices, water detecting devices, waterabsent detecting devices, motion detecting devices, and event detectingdevices.

EXAMPLE 22

Non-limiting examples of sensor identity names for open/close devicesinclude: Door, Window, Back Door, Basement Door, Basement Window,Bathroom Window, Bedroom Door, Bedroom Window, Deck Door, Front Door,Kitchen Door, Kitchen Window, Garage Door, Living Rm Window (or LivingRoom Window), Pantry, Pet Door, Storage Area, Supply Room, Cabinet,Closet, Drawer, Gun Cabinet, Jewelry Box, Mail Box, Refrigerator, Safe,Trunk, and TV/Stereo Cabinet.

EXAMPLE 23

Non-limiting examples of sensor identity names for on/off devicesinclude: Appliance, Clothes Iron, Coffee Maker, Curling Iron, GameSystem, Light, Refrigerator, Stereo, Stove, Toaster Oven, and TV.

EXAMPLE 24

Non-limiting examples of sensor identity names for water detectingdevices (e.g., an alarm is generated if water is detected) include:Basement Floor, Bathroom Floor, Bed Room, Dining Room, Garage, LaundryRoom, Living Room, Storage Area, Sump Pump, Under Sink, and UtilitySink.

EXAMPLE 25

Non-limiting examples of sensor identity names for water absentdetecting devices (e.g., an alarm is generated if water is not detected)include: Cat Bowl, Dog Bowl, Fish Tank, Garden, Pool, and Water Bowl.

EXAMPLE 26

Non-limiting examples of sensor identity names for motion detectingdevices include: Attic, Baby Room, Back Door, Basement, Driveway, Front,Garage, Hallway, Kitchen, and Pantry.

EXAMPLE 27

Non-limiting examples of sensor identity names for event detectors(e.g., which might respond, for example, to a pushbutton or other userinput) include: Help!, Get Milk!, Come Down Here, Come Up Here, I'mHome, Doorbell, Keyfinder, and Community Watch.

As was discussed above in connection with FIG. 9B, during the sensorconfiguration, the fob 6 and the sensor 10 are communicating (e.g., viaRF) with the base station 4 for the storage of configuration details.This is initiated, for example, as a result of the physical mating ofthe fob 6 and the particular sensor, such as 10. Although theconfiguration appears, from the user's perspective, as if it is takingplace locally (directly), it is actually being mediated by the basestation 4. This permits the base station 4 to store/log criticalinformation in nonvolatile memory and/or to report it remotely.

The fob user interface (e.g., FIG. 5F) represents a single, personal“tear off” (e.g., the fob 6 is both removable from the base station 4 orfrom one of the sensors 8,10,12 and, also, is portable) display andsetup device for every aspect of the system 2. Preferably, the userlearns the procedure once (e.g., for the base station 4 (FIG. 6A) or foran initial sensor, such as sensor 207 of FIG. 6B) and employs thatprocedure for the other sensors 8,10,12 of the system 2. In this manner,the base station 4 and the sensors, such as 8 of FIG. 4B, are “headless”and simply “dock” with, “mate” with or are proximate the fob 6 when andwhere needed. This procedure acts as a logical constraint on theproliferation of nonstandard user interface elements within the systemenvironment. Hence, rather than solve a particularly vexing userinterface problem on a given component by, for example, adding buttonsto the component and adding instructions to a user's guide, the “tearoff” fob user interface affords a flexible, potentially deep, consistentgraphical interface for both relatively low cost and relatively highcost/complex components.

The mating of the fob 6 to the system component (e.g., base station 4;sensor 10) provides for an associative/semantic “training” of newcomponents to personalize the system 2 and to provide a given uniquehome/structure and location. This mechanical mating allows for thesystem 2 to provide context/location specific display and setupinteraction using, for example, physical sensor location as a filteringmechanism, which significantly reduces the overall perceived complexityof the interface. This, further, allows for a “one button/dial”interaction physics on the fob 6. Examples 28-37 and 39, below, furtherdescribe examples of the fob mating procedure.

EXAMPLE 28

Known current systems require the user to: (1) memorize a sensor number;(2) mount the sensor in place in the home (e.g., possibly out of rangeof its main control board); (3) set any sensor specific configurationswitches; (4) return to the main control board and test the sensor; (5)associate the memorized sensor number with a, typically, writtenname/number mapping; and (6) repeat steps (1)-(5) for each of thesensors, while setting distinct and different configuration switches oneach sensor. Alternatively, each sensor requires a unique (and usuallydifferent) display and input mechanism, in order to learn and program(e.g., different switch(es), knob(s), screen(s) and/or button(s)) on aremote control.

In contrast, the present system 2 employs a single interface “physics”in which the fob rotating knob 138 of FIG. 5F is rotated to scrollthrough (and/or highlight) various links or information, and the fobbutton 152 is pressed to select the highlighted link or information. Aspart of the configuration, the personal interface fob 6 is physicallypaired or otherwise suitably mated with the component (e.g., sensor 10;base station 4) to be configured. Then, the user reads and answersquestions that pop-up on this, now active, component's display on thefob 6 using the above-described single interface “physics”. Then, theuser places the component in the desired location in the home. Forexample, if the user walks out of range of the base station 4, the matedfob 6 and component, such as the sensor 10, preferably informs the userof the “out of range” condition. Finally, based on the desired location(e.g., door) and type (e.g., open/closed detector) of component, theuser may readily customize it accordingly (e.g., a door sensorautomatically displays a list of common names, such as, for example,“Front Door” and “Deck Door”).

In this example, the physical pairing of the fob 6 and sensor 10 allowsfor the filtering of the various interface items (e.g., if paired with adoor sensor, then don't show a menu of water detector sensors). Also,the physical location at the time of pairing in the desired environmentallows for the filtering of the functionality (e.g., if the sensor 10 is“out of range” of the base station 4, then the fob 6 will display “outof range,” which signals to the user that they have exceeded thefunctional range of the sensor 10).

EXAMPLE 29

FIG. 13 shows a sensor 460 having a female connector 462 and a proximatefob 464 having a male connector 466 (e.g., a USB style bayonetconnector). FIG. 14 shows the mated pair of the sensor 460 and fob 464in which the male connector 466 is inserted within the female connector462, in order to provide the signature (e.g., address; serial number) ofthe sensor 460 directly to the fob 464. This physical “key” fob 464provides the user with a sense of security in the system 2 of FIG. 1 by“activating” each system component, such as the sensor 460, through theprocess of “keying” or mating with it. Alternatively, the sensor 460 maywirelessly communicate its signature to the base station 4, rather thanto the fob 464.

EXAMPLE 30

FIGS. 11 and 12 show another fob 470 which employs a recessed “key”notch 472 to engage a base station 474 and sensor 476, respectively. Ascontrasted with Example 29, this shortens the overall length of the fob470 by making the electrical connection be part of a slide (e.g.,including two longitudinally positioned electrical contacts 478,480) inthe recessed “key” notch 472, rather than the USB style bayonetconnector 466 of FIG. 13. Those contacts 478,480, in this example,electrically and mechanically engage a conductor 481 in the base station474.

EXAMPLE 31

FIG. 15 shows the resulting mating of the fob 470 with the RF sensor 476having an antenna 477. In this example, the fob 470 may still generallylook like a key, although when it is mated, or otherwise “locked up”with the sensor 476, it mimics a “pop-up” display interface 482. Thiseffectively creates an ad-hoc, location-linked “customizable” sensordisplay for adjustment of a “headless” component, such as the sensor476.

EXAMPLE 32

FIG. 16 shows an example of the sensor/base program switch 74 of a fob6?, and the sensor program switch 104 of a sensor 10?. The fob 6?includes a case or enclosure 490 having an opening 492, a protrusion 494and a printed circuit board 496 therein. The sensor/base program switch74 is proximate the opening 492, and the sensor program switch 104 is ona printed circuit board 497 and proximate the opening 498 of the sensorcase or enclosure 500. Whenever the fob 6? is suitably mated with thesensor 10?, the fob protrusion 494 passes through the sensor opening 498and engages the sensor program switch 104. At the same time, wheneverthe sensor 10? is suitably mated with the fob 6?, the sensor protrusion502 passes through the fob opening 492 and engages the sensor/baseprogram switch 74.

EXAMPLE 33

The configuration (or binding) mechanism permits the headless basestation 4 to associate a particular sensor, such as 10, with acorresponding name (Open-Close) and location (Front Door). First, theportable fob 6 is taken to the particular sensor 10 to be configured aspart of the system 2. Next, the fob 6 and the particular sensor 10 aresuitable connected, in order that the fob 6 can associate the sensor'sidentifying signature (e.g., address; serial number) with acorresponding graphical identifier (e.g., label; symbol; icon) on thefob display 78 of FIG. 3. In turn, that information is wirelesslycommunicated from the fob 6 and/or sensor 10 to the headless basestation 4.

EXAMPLE 34

Preferably, the fob 6 employs a relatively simple instruction manualand/or an intuitive sequence of operating steps, in order to provide anout-of-the-box experience for the user. The fob 6 is either temporarilyor momentarily mated or otherwise associated with the sensor 10 in orderto “learn” the sensor's identifying signature (e.g., address; serialnumber) and “label” that information with the corresponding graphicalidentifier (e.g., label; symbol; icon) on the fob display 78. In thismanner, the system 2 may “key” the new sensor 10 to the home's system 2,rather than to a neighbor's system (not shown). Also, the system 2 may“key” only the home's sensors 8,10,12 to the home's system 2, ratherthan any of the neighbor's sensors (not shown). Further, this permitsnew sensors, such as 207 of FIG. 6B, to be easily added on the system 2and to train or associate them with unique locations and environments inor about the home.

EXAMPLE 35

The connection mechanism between the fob 464 and the sensor 460 of FIG.13 may be physical (e.g., employing mechanically and electrically matingconnectors 466,462 on both the fob 464 and the sensor 460), in order tocommunicate the sensor's presence to the fob 464, and in order tocommunicate the sensor's identifying signature (e.g., address; serialnumber) to the fob 464 and/or base station 4.

EXAMPLE 36

The connection mechanism between a fob and a sensor may be wireless(e.g., optical; RF on both the fob and the sensor), in order tocommunicate the sensor's presence to the fob, and in order tocommunicate the sensor's identifying signature (e.g., address; serialnumber) to the base station.

EXAMPLE 37

In some instances, the location of the sensor in the system 2, might besuch that the sensor is difficult to access. One example is a sensor fora ceiling light fixture, which is difficult to directly access, exceptby, for example, employing a ladder or similar device. Hence, the sensorand fob may employ a proximity sensor (not shown) and/or an optical port(not shown), which detects when the fob is within a suitable distance ofthe sensor.

EXAMPLE 38

Although a fob 6, which mimics the shape of a “key,” has been disclosed,a wide range of other suitable shapes and sizes of fobs may be employed.For example, other embodiments of such fobs may be in the form of apendant, a credit card or other object that is directly or indirectlycarried and/or worn by a person. Such fobs, for example, may be attachedto and/or placed on another household object (e.g., a refrigerator; atable), and/or attached to or carried by a personal object (e.g., apurse; a wallet; a credit card case).

EXAMPLE 39

FIGS. 17A-17C show an example of another fob 510 and a wireless systemcomponent 512 (e.g., a sensor; a base station), which are suitably matedfor configuration of the system component 512 and/or the fob 510. Thefob 510 includes a training/mating switch 514, which functions in themanner of the sensor/base program switch 74 of FIG. 3. The component 512includes a surface or protrusion 516, which is designed to engage theswitch 514. The component 512 also includes a training/mating switch 518having an actuator 519, which functions in the manner of the baseprogram switch 42 of FIG. 2A or the sensor program switch 104 of FIG.4A. The fob includes a protrusion or surface 520, which is designed toengage the switch actuator 519.

Initially, as shown in FIGS. 17A and 17B, the fob 510 is slid into thecomponent 512. For example, the fob 510 includes an engagement portion522 having a tongue 524, while the component 512 has a correspondingmating engagement recess 526 (shown in hidden line drawing) with acorresponding groove 528. As the component protrusion 516 approaches thefob switch 514, it engages and activates an actuator 530 thereon, asshown in FIG. 17C. At the same time, as the fob surface 520 approachesthe component switch actuator 519, it engages and activates thatactuator 519, as shown in FIG. 17C. In turn, when the fob 510 andcomponent 512 are completely seated, with both switches 514,518 beingactivated, the fob 510 and component 512 may establish RF communicationswith the base station 4 of FIG. 1 as was discussed above in connectionwith FIGS. 9A and 9B. In this example, the component switch 518 isactivated just before the fob switch 514. Alternatively, the switches514,518 may be activated at the same or different times. Also, in theexample, the component switch 518 may be a two-pole device, which isdesigned to detect both insertion and removal of the fob 510.

The exemplary home system 2 provides a homeowner with both in-home(referred to as “home alone”) and away from home (referred to as “outand about”) seven days a week, 24 hours a day awareness of the“wellness” of the home.

While for clarity of disclosure reference has been made herein to theexemplary display 78 for displaying home wellness system information andvalues, it will be appreciated that such information, such values, otherinformation and/or other values may be stored, printed on hard copy, becomputer modified, or be combined with other data. All such processingshall be deemed to fall within the terms “display” or “displaying” asemployed herein.

While specific embodiments of the invention have been described indetail, it will be appreciated by those skilled in the art that variousmodifications and alternatives to those details could be developed inlight of the overall teachings of the disclosure. Accordingly, theparticular arrangements disclosed are meant to be illustrative only andnot limiting as to the scope of the invention which is to be given thefull breadth of the claims appended and any and all equivalents thereof.

1. A system for a structure, said system for a structure comprising: a server including a wireless transceiver; a plurality of sensors, each of said sensors including a wireless transceiver adapted to communicate sensor information to the wireless transceiver of said server; and a portable fob including a user input device, a display and a wireless transceiver adapted to communicate with the wireless transceiver of said server, said user input device and said display cooperating to provide at least one of a first rotary menu for displaying said sensor information of said sensors and a second rotary menu for configuring said sensors.
 2. The system for a structure of claim 1 wherein at least one of said first rotary menu and said second rotary menu form a rotary menu selected by said user input device.
 3. The system for a structure of claim 2 wherein said user input device is a rotary encoder including a selector button.
 4. The system for a structure of claim 3 wherein said rotary encoder is a thumbwheel encoder including said selector button.
 5. The system for a structure of claim 4 wherein said first rotary menu forms said rotary menu; and wherein said thumbwheel encoder scrolls through a list of sensor names and graphical objects on said rotary menu in response to said thumbwheel encoder in order to display at least some of said sensor information.
 6. The system for a structure of claim 5 wherein said sensors communicate sensor state information to said server; wherein said server communicates said sensor state information to said portable fob; and wherein said selector button selects one of said sensor names on said rotary menu in order to display said sensor state information for said selected one of said sensor names.
 7. The system for a structure of claim 5 wherein said first rotary menu has a top and a bottom; and wherein said thumbwheel encoder scrolls directly between the top and the bottom of said first rotary menu.
 8. The system for a structure of claim 5 wherein said sensor information includes sensor state information; and wherein said graphical objects display said sensor state information.
 9. The system for a structure of claim 4 wherein said second rotary menu forms said rotary menu; and wherein said thumbwheel encoder scrolls through a list of potential sensor names on said rotary menu in order to name one of said sensors in response to said selector button.
 10. The system for a structure of claim 9 wherein said second rotary menu has a top and a bottom; and wherein said thumbwheel encoder scrolls directly between the top and the bottom of said second rotary menu.
 11. The system for a structure of claim 1 wherein said server further includes a processor, which detects a state change from the sensor information of one of said sensors, and which sends said state change from the wireless transceiver of said server to the wireless transceiver of portable fob; and wherein said portable fob further includes a processor, which responsively displays said first rotary menu if said state change is received.
 12. The system for a structure of claim 1 wherein said portable fob further includes a port, which detects if said portable fob is mated with or proximate to another component, and also includes a processor, which responsively displays said second rotary menu when said portable fob is mated with or proximate to said another component.
 13. A portable fob for a system for a structure, said system for a structure including a server and a plurality of sensors, said portable fob comprising: a portable housing; a wireless communication port adapted for wireless communication with said server; a user input device; and a display, said user input device and said display cooperating to provide at least one of a first rotary menu for displaying information from said server for at least one of said sensors and a second rotary menu for configuring at least one of said sensors at said server.
 14. The portable fob of claim 13 wherein at least one of said first rotary menu and said second rotary menu form a rotary menu selected by said user input device.
 15. The portable fob of claim 13 wherein said user input device is a rotary encoder including a selector button.
 16. The portable fob of claim 15 wherein said rotary encoder is a thumbwheel encoder including said selector button.
 17. The portable fob of claim 13 wherein said first rotary menu forms said rotary menu; and wherein said user input device includes a rotary member, which rotates to scroll through a list of sensor names and graphical objects on said rotary menu in response to said rotation in order to display at least some of said sensor information.
 18. The portable fob of claim 17 wherein said sensors communicate sensor state information to said server; wherein said server communicates said sensor state information to said portable fob; and wherein said user input device further includes a selector button to select one of said sensor names on said rotary menu in order to display said sensor state information for said selected one of said sensor names.
 19. The portable fob of claim 17 wherein said first rotary menu has a top and a bottom; and wherein said rotary member scrolls directly between the top and the bottom of said first rotary menu.
 20. The portable fob of claim 17 wherein said displayed information from said server includes sensor state information; and wherein said graphical objects display said sensor state information.
 21. The portable fob of claim 13 wherein said second rotary menu forms said rotary menu; wherein said user input device includes a rotary member and a selector button; wherein said rotary member rotates to scroll through a list of potential sensor names on said rotary menu; and wherein said selector button selects one of said potential sensor names to name one of said sensors.
 22. The portable fob of claim 21 wherein said second rotary menu has a top and a bottom; and wherein said rotary member scrolls directly between the top and the bottom of said second rotary menu. 